Skip to content
This repository was archived by the owner on Sep 8, 2026. It is now read-only.

repo: point this repo and its doublezero-solana deps at the malbeclabs org - #412

Merged
bgm-malbeclabs merged 1 commit into
mainfrom
chore/transfer-to-malbeclabs
Aug 26, 2026
Merged

repo: point this repo and its doublezero-solana deps at the malbeclabs org#412
bgm-malbeclabs merged 1 commit into
mainfrom
chore/transfer-to-malbeclabs

Conversation

@bgm-malbeclabs

Copy link
Copy Markdown
Collaborator

Ahead of moving doublezero-offchain and doublezero-solana from the doublezerofoundation org to malbeclabs.

⚠️ Do not merge before the transfer

CI on this PR fails, and that is expected. malbeclabs/doublezero-solana does not exist yet, so cargo cannot resolve the new dep URL. The same reason makes the local pre-commit clippy hook fail, so the commit skipped it.

Merge order: transfer both repos, then merge this, then re-run CI.

What changed

File Change Why
release/.goreleaser.*.yaml (5) owner: doublezerofoundationmalbeclabs The one real breakage. GoReleaser writes the GitHub release to the owner named here. The new repo's GITHUB_TOKEN has no write access to the old org, so every release workflow fails until this lands.
Cargo.toml 3 doublezero-solana git deps Tag revenue-distribution/v0.3.7 is unchanged, so the same commit resolves from the new URL.
Cargo.lock 3 matching source = lines URL swap only. The pinned sha 4368da2c does not change, so no re-resolution.
Cargo.toml repository, homepage Crate metadata.
scripts/install-doublezero-solana.sh REPO= and 4 curl examples Public install path validators run.
CONTRIBUTING.md doublezero-rewarderdoublezero-offchain That old name already redirects here. Left alone it would take two hops after the transfer.

Deliberately left alone

  • network-shapley-rs stays on doublezerofoundation. That repo is not moving and it is public, so the dep keeps working. Possible follow-up.
  • CHANGELOG.md link footers (~14 files). GitHub keeps redirects for old PR and release URLs, so these stay correct.

Not a code change, still needed

  • Re-add the four repo Actions secrets if the transfer drops them: CLOUDSMITH_TOKEN, GORELEASER_KEY, SLACK_BOTS_WEBHOOK, MALBECLABS_DOUBLEZERO_SSH. The SSH one looks unused, every git dep is public.
  • Check the main ruleset and the copilot environment survived.
  • Cloudsmith is unaffected. Those repos (doublezero, doublezero-testnet, doublezero-devnet) live on Cloudsmith, not GitHub, and the apt package names do not change.

@bgm-malbeclabs
bgm-malbeclabs marked this pull request as ready for review August 26, 2026 20:22
…s org

Ahead of the transfer of doublezero-offchain and doublezero-solana from the
doublezerofoundation org to malbeclabs.

- The three doublezero-solana workspace git deps, and the matching Cargo.lock
  source lines. The pinned tag and commit do not change, so cargo resolves the
  same code from the new URL.
- Release owner in the five goreleaser configs. This one breaks releases if we
  leave it. GoReleaser writes the GitHub release to the owner named here, and
  the new repo's GITHUB_TOKEN cannot write to the old org.
- REPO and the curl examples in scripts/install-doublezero-solana.sh, which
  validators run to install the CLI.
- repository and homepage in the workspace manifest.
- CONTRIBUTING.md, which still named doublezero-rewarder. That name already
  redirects here, so the links would take two hops after the transfer.

The network-shapley-rs dep stays on doublezerofoundation. That repo is not
moving and it is public, so it keeps working.

CHANGELOG links to old pull requests and releases stay as they are. GitHub
keeps redirects for those.

Do not merge before the transfer. Until malbeclabs/doublezero-solana exists,
cargo cannot resolve the new URL and every build fails. The pre-commit clippy
hook fails for that same reason, so this commit skipped it.
@bgm-malbeclabs
bgm-malbeclabs force-pushed the chore/transfer-to-malbeclabs branch from a9028ed to 927d66e Compare August 26, 2026 20:24
@bgm-malbeclabs
bgm-malbeclabs enabled auto-merge (squash) August 26, 2026 20:33
@bgm-malbeclabs
bgm-malbeclabs merged commit 0c84bde into main Aug 26, 2026
6 checks passed
@bgm-malbeclabs
bgm-malbeclabs deleted the chore/transfer-to-malbeclabs branch August 26, 2026 20:39
bgm-malbeclabs added a commit to malbeclabs/doublezero that referenced this pull request Aug 28, 2026
…s org (malbeclabs/doublezero-offchain#412)

Ahead of moving `doublezero-offchain` and `doublezero-solana` from the
`doublezerofoundation` org to `malbeclabs`.

## ⚠️ Do not merge before the transfer

CI on this PR fails, and that is expected.
`malbeclabs/doublezero-solana` does not exist yet, so cargo cannot
resolve the new dep URL. The same reason makes the local pre-commit
clippy hook fail, so the commit skipped it.

Merge order: transfer both repos, then merge this, then re-run CI.

## What changed

| File | Change | Why |
|---|---|---|
| `release/.goreleaser.*.yaml` (5) | `owner: doublezerofoundation` →
`malbeclabs` | **The one real breakage.** GoReleaser writes the GitHub
release to the owner named here. The new repo's `GITHUB_TOKEN` has no
write access to the old org, so every release workflow fails until this
lands. |
| `Cargo.toml` | 3 `doublezero-solana` git deps | Tag
`revenue-distribution/v0.3.7` is unchanged, so the same commit resolves
from the new URL. |
| `Cargo.lock` | 3 matching `source =` lines | URL swap only. The pinned
sha `4368da2c` does not change, so no re-resolution. |
| `Cargo.toml` | `repository`, `homepage` | Crate metadata. |
| `scripts/install-doublezero-solana.sh` | `REPO=` and 4 curl examples |
Public install path validators run. |
| `CONTRIBUTING.md` | `doublezero-rewarder` → `doublezero-offchain` |
That old name already redirects here. Left alone it would take two hops
after the transfer. |

## Deliberately left alone

- **`network-shapley-rs`** stays on `doublezerofoundation`. That repo is
not moving and it is public, so the dep keeps working. Possible
follow-up.
- **CHANGELOG.md link footers** (~14 files). GitHub keeps redirects for
old PR and release URLs, so these stay correct.

## Not a code change, still needed

- Re-add the four repo Actions secrets if the transfer drops them:
`CLOUDSMITH_TOKEN`, `GORELEASER_KEY`, `SLACK_BOTS_WEBHOOK`,
`MALBECLABS_DOUBLEZERO_SSH`. The SSH one looks unused, every git dep is
public.
- Check the `main` ruleset and the `copilot` environment survived.
- Cloudsmith is unaffected. Those repos (`doublezero`,
`doublezero-testnet`, `doublezero-devnet`) live on Cloudsmith, not
GitHub, and the apt package names do not change.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants